Update prepare-pipelines.yml to use the new jobs-based template #4187
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
konrad-jamrozik
requested review from
danieljurek,
weshaggard and
benbp
as code owners
konrad-jamrozik
added
the
Central-EngSys
antkmsft
approved these changes
Dec 13, 2022
weshaggard
approved these changes
Dec 13, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
This is an Azure SDK Engineering System Team PR, made to address failing prepare-pipelines pipeline, as explained in Azure/azure-sdk-tools#4888. The issue is currently mitigated with a manual configuration override of the machine pool used. This PR is a proper fix.
This PR is a follow-up PR to Azure/azure-sdk-tools#4930.
Changes made
This PR rewires
prepare-pipelines.ymlto use the new template introduced by Azure/azure-sdk-tools#4930. This template sets, viapooldefinition, the Ubuntu image used by theprepare-pipelinespipeline, thus properly addressing the issue. See that PR description for more context.Testing done
See section on testing in Azure/azure-sdk-tools#4930